Unexpected breaks in voice input
# support
p
Copy code
Model output: 12:30 PM or 1PM?
Voice input: One<break time="0.5s" />Two<break time="0.5s" />Three<break time="0.5s" />Zero P M, or 1 P M?
Are there ways to prevent this from happening? call id :
492472e2-5ea8-4b52-96c2-12dfe23b801b
v
@progremir It seems like there might be an issue with the way the voice input is being interpreted or synthesized. To prevent such occurrences, you can consider the following strategies: 1. **Adjusting Silence Timeout**: If the system is cutting off due to pauses in speech, you might want to increase the
silenceTimeoutSeconds
to allow for longer natural pauses in conversation. 2. **Response Delay**: Ensure that the
responseDelaySeconds
is set appropriately to prevent the assistant from responding too quickly, which might cause it to misinterpret the end of the user's speech. 3. **Pronunciation and Pauses**: Work on the pronunciation and timing of the voice inputs to ensure that the text-to-speech engine can clearly distinguish between words and numbers. 4. **Voice Recognition Training**: If possible, train the voice recognition system with varied speech patterns and numbers to improve its accuracy. 5. **Input Validation**: Implement input validation to confirm with the user if the recognized time is correct. Would you like me to adjust any of these settings for you based on the call ID provided?
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
c
I'm experiencing the same thing, only since this morning. Call ID: aef3e996-2305-4e80-8dee-0915ad764128. Voice input: we also have options at TwoFiveZero in the afternoon and ThreeOneZero in the afternoon on Friday.
For me it's much better by disabling, "inputReformattingEnabled": false, and changing the provider from 11labs to openai: { "speed": 1.1, "voiceId": "onyx", "provider": "openai", "inputReformattingEnabled": false, "inputPunctuationBoundaries": [ ".", "?", "!" ] }
p
@User
s
We were working on improving the pronunciation of numbers and it didn’t worked out pretty well
Anyways, we have reverted the changes
so it work properly now
c
oh ok, good to know, good news. Thank you for checking it. I thought it had something to do with that as it was resolved when disabling reformatting. We will test with it back enabled now.
10 Views